DATAMONGO-1058 - DBRef should respect explicit field name. #227
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prepare issue branch.
We now use property.getFieldName() for mapping DbRefs. This assures we also capture explicitly defined names set via @field.
|
Picked into master via: 458fe4f. |
|
What are the minor glitches for 1.5.0? |
|
just some conflicts in one of the test classes as there are changes for text search in there as well that do not exist on 1.5. So one has to remove those. |
|
Back ported to 1.6.x and 1.5.x. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now use
property.getFieldName()for mappingDbRefs. This assures we also capture explicitly defined names set via@Field.Should be back ported to
1.6.x.Can be back ported to
1.5.x. Minor glitches there but still can be done.